What

The SQL editor's Bridge query badge now appears for any Iceberg-tiered topic, including ones that haven't synced to Iceberg yet.

Why

The badge was gated on the presence of an Iceberg lag metric, not on whether the topic is actually Iceberg-tiered:

// sql-workspace.tsx (before)
const tx = bridgeTxLag.data?.results?.[0]?.value?.value;
const commit = bridgeCommitLag.data?.results?.[0]?.value?.value;
if (tx === undefined && commit === undefined) {
  return; // → run.bridge undefined → badge hidden
}

A freshly-tiered topic that hasn't started translating yet emits no iceberg_topic_translation_lag / iceberg_topic_commit_lag series, so bridge resolved to undefined and the query — with every row served from the topic tail — was misclassified as a plain query and showed no badge. This is exactly the case where the bridge is doing the most work.

Fix

Decouple bridge classification from lag display:

• Classify bridge-ness from the authoritative redpanda.iceberg.mode config via useTopicIcebergQuery (already used by the catalog tree), independent of lag-metric availability.
• Lag values default to 0 when their series is absent; the lag timeline stays hidden until real lag appears (unchanged totalLag === 0 guard), but the badge now shows for any tiered topic.
• Bonus correctness: a non-tiered topic now correctly shows no badge because the config says so, not because a metric happened to be missing.

Testing

• tsgo --noEmit clean
• SQL unit tests pass (sql.test.tsx)
• No new lint errors introduced